<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. Setup</title><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot" /><meta name="keywords" content="ISO C++, library" /><meta name="keywords" content="ISO C++, runtime, library" /><link rel="home" href="../index.html" title="The GNU C++ Library" /><link rel="up" href="intro.html" title="Part I.  Introduction" /><link rel="prev" href="bugs.html" title="Bugs" /><link rel="next" href="configure.html" title="Configure" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Setup</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="bugs.html">Prev</a> </td><th width="60%" align="center">Part I. 
  Introduction
  
</th><td width="20%" align="right"> <a accesskey="n" href="configure.html">Next</a></td></tr></table><hr /></div><div class="chapter"><div class="titlepage"><div><div><h2 class="title"><a id="manual.intro.setup"></a>Chapter 2. Setup</h2></div></div></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="section"><a href="setup.html#manual.intro.setup.prereq">Prerequisites</a></span></dt><dt><span class="section"><a href="configure.html">Configure</a></span></dt><dt><span class="section"><a href="make.html">Make</a></span></dt></dl></div><p>Transforming libstdc++ sources into installed include files
   and properly built binaries useful for linking to other software is
   done as part of building GCC. Building libstdc++ separately from the
   rest of GCC is not supported.
   </p><p>The general outline of commands to build GCC is something like:
   </p><pre class="programlisting">
   <em class="replaceable"><code>get gcc sources</code></em>
   <em class="replaceable"><code>extract into gccsrcdir</code></em>
   mkdir <em class="replaceable"><code>gccbuilddir</code></em>
   cd <em class="replaceable"><code>gccbuilddir</code></em>
   <em class="replaceable"><code>gccsrcdir</code></em>/configure --prefix=<em class="replaceable"><code>destdir</code></em> --other-opts...
   make
   make check
   make install
   </pre><p>
     Each step is described in more detail in the following sections.
   </p><div class="section"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="manual.intro.setup.prereq"></a>Prerequisites</h2></div></div></div><p>
  Because libstdc++ is part of GCC, the primary source for
   installation instructions is
   <a class="link" href="https://gcc.gnu.org/install/" target="_top">the GCC install page</a>.
   In particular, list of prerequisite software needed to build the library
   <a class="link" href="https://gcc.gnu.org/install/prerequisites.html" target="_top">
   starts with those requirements.</a> The same pages also list
   the tools you will need if you wish to modify the source.
</p><p>
   Additional data is given here only where it applies to libstdc++.
  </p><p>To take full advantage of useful space-saving features and
      bug-fixes you should use a recent binutils whenever possible.
      The configure process will automatically detect and use these
      features if the underlying support is present.
   </p><p>
     To generate the API documentation from the sources you will need
     Doxygen, see <a class="link" href="documentation_hacking.html" title="Writing and Generating Documentation">Documentation
     Hacking</a> in the appendix for full details.
   </p><p>
   Finally, a few system-specific requirements:
   </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">linux</span></dt><dd><p>
	  The 'gnu' locale model makes use of <code class="function">iconv</code>
	  for character set conversions. The relevant functions are provided
	  by Glibc and so are always available, however they can also be
	  provided by the separate GNU libiconv library. If GNU libiconv is
	  found when GCC is built (e.g., because its headers are installed
	  in <code class="filename">/usr/local/include</code>)
	  then the <code class="filename">libstdc++.so.6</code> library will have a
	  run-time dependency on <code class="filename">libiconv.so.2</code>.
	  If you do not want that run-time dependency then you should do
	  one of the following:
	</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
	      Uninstall the libiconv headers before building GCC.
	      Glibc already provides <code class="function">iconv</code> so you should
	      not need libiconv anyway.
	    </p></li><li class="listitem"><p>
	    <a class="link" href="https://www.gnu.org/software/libiconv/#downloading" target="_top">
	    Download</a> the libiconv sources and extract them into the
	    top level of the GCC source tree, e.g.,
	    </p><pre class="programlisting">
wget https://ftp.gnu.org/pub/gnu/libiconv/libiconv-1.16.tar.gz
tar xf libiconv-1.16.tar.gz
ln -s libiconv-1.16 libiconv
</pre><p>
	      This will build libiconv as part of building GCC and link to
	      it statically, so there is no <code class="filename">libiconv.so.2</code>
	      dependency.
	    </p></li><li class="listitem"><p>
	      Configure GCC with <code class="option">--with-libiconv-type=static</code>.
	      This requires the static <code class="filename">libiconv.a</code> library,
	      which is not installed by default. You might need to reinstall
	      libiconv using the <code class="option">--enable-static</code> configure
	      option to get the static library.
	    </p></li></ul></div><p>
	  If GCC 3.1.0 or later on is being used on GNU/Linux, an attempt
	  will be made to use "C" library functionality necessary for
	  C++ named locale support, e.g. the <code class="function">newlocale</code>
	  and <code class="function">uselocale</code> functions.
	  For GCC 4.6.0 and later,
	  this means that glibc 2.3 or later is required.
	</p><p>
	  If the 'gnu' locale model is being used, the following
	  locales are used and tested in the libstdc++ testsuites.
	  The first column is the name of the locale, the second is
	  the character set it is expected to use.
	</p><pre class="programlisting">
de_DE               ISO-8859-1
de_DE@euro          ISO-8859-15
en_GB               ISO-8859-1
en_HK               ISO-8859-1
en_PH               ISO-8859-1
en_US               ISO-8859-1
en_US.ISO-8859-1    ISO-8859-1
en_US.ISO-8859-15   ISO-8859-15
en_US.UTF-8         UTF-8
es_ES               ISO-8859-1
es_MX               ISO-8859-1
fr_FR               ISO-8859-1
fr_FR@euro          ISO-8859-15
is_IS               UTF-8
it_IT               ISO-8859-1
ja_JP.eucjp         EUC-JP
ru_RU.ISO-8859-5    ISO-8859-5
ru_RU.UTF-8         UTF-8
se_NO.UTF-8         UTF-8
ta_IN               UTF-8
zh_TW               BIG5
</pre><p>Failure to have installed the underlying "C" library
      locale information for any of the above regions means that
      the corresponding C++ named locale will not work:  because of
      this, the libstdc++ testsuite will skip named locale tests
      which need missing information.  If this isn't an issue, don't
      worry about it.  If a named locale is needed, the underlying
      locale information must be installed.  Note that rebuilding
      libstdc++ after "C" locales are installed is not necessary.
      </p><p>
	To install support for locales, do only one of the following:
      </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>install all locales, e.g., run
	    <code class="code"> dnf install glibc-all-langpacks </code>
	    for Fedora and related distributions.
	  </p></li><li class="listitem"><p>install just the necessary locales</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>with Debian GNU/Linux:</p><p> Add the above list, as shown, to the file
	      <code class="code">/etc/locale.gen</code> </p><p> run <code class="code">/usr/sbin/locale-gen</code> </p></li><li class="listitem"><p>on most Unix-like operating systems:</p><p><code class="code"> localedef -i de_DE -f ISO-8859-1 de_DE </code></p><p>(repeat for each entry in the above list) </p></li><li class="listitem"><p>
	       Instructions for other operating systems solicited.
	    </p></li></ul></div></li></ul></div>
	Some tests for the <code class="code">std::messages</code> facet require a
	message catalog created by the <span class="command"><strong>msgfmt</strong></span> utility.
	That is usually installed as part of the GNU gettext library.
	If <span class="command"><strong>msgfmt</strong></span> is not available, some tests under
	the <code class="filename">22_locale/messages</code>
	directory will fail.
      </dd></dl></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="bugs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="intro.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="configure.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Bugs </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> Configure</td></tr></table></div></body></html>